[junit] Fix JUnit generated XML report. #123
Conversation
|
Update: actually version 1.33 of the Jenkins JUnit plugin has fixed the occurring NPE which was present during the plugin execution in version before. So even though there is no working issue now, still formally the XSD schema requires the I'll keep on your decision whether you feel more to merge/update or close this. |
Based on the Maven surefire-plugin JUnit XSD schema [1], `name` attribute in `testcase` is required. Let's use description value that is currently used as `classname` attribute for this purpose. This issue may lead to errors with JUnit plugin 1.32 for Jenkins. [1] https://maven.apache.org/surefire/maven-surefire-plugin/xsd/surefire-test-report.xsd
jstourac
force-pushed
the
fixJunitReport
branch
from
0fba6b3
to
72a6b9b
Compare
|
Hi there :) Is there any chance this gets merged? Even though this doesn't make problem to the Jenkins plugin anymore, it still violates the XSD format expected by the Maven surefire plugin. Or shall we follow some different XSD instead that one? |
|
I'm also running into this as I'm attempting to show h2spec results from CI using a GitHub action like test-reporter - I suspect that's where it's choking: edit: that was it, this patch fixes it for me: https://github.com/hapsoc/hring/actions/runs/3856947194/jobs/6573802085 |
Based on the Maven surefire-plugin JUnit XSD schema [1],
nameattribute in
testcaseis required. Let's use description valuethat is currently used as
classnameattribute for this purpose.This issue may lead to errors with JUnit plugin 1.32 for Jenkins.
[1] https://maven.apache.org/surefire/maven-surefire-plugin/xsd/surefire-test-report.xsd